Introduction to Agile and Scrum

Quick Links

1. Overview of Software Process Models

Prescriptive Process Models

  • Bring structure and order to software development
  • Framework activities:
    • Communication
    • Planning
    • Modeling
    • Construction
    • Deployment
  • Sequential models (waterfall, V-model) - oldest but less suitable for modern development
  • Incremental models - iterative with rapid working versions

2. What is Scrum?

Definition

  • Agile process focusing on highest business value in shortest time
  • Rapid inspection of working software (2-4 weeks)
  • Business-driven priorities with self-organizing teams
  • Regular review cycles with working software

Key Characteristics

  • Self-organizing teams
  • "Sprints" of 2-4 weeks
  • Product backlog-driven
  • Flexible engineering practices
  • Generative rules for agile environment

3. Scrum Framework Components

Roles

Product Owner

  • Defines product features
  • Manages release schedule
  • Oversees ROI
  • Prioritizes features
  • Accepts/rejects deliverables

ScrumMaster

  • Management representative
  • Process guardian
  • Impediment remover
  • Productivity enabler
  • Team protector

Team

  • 5-9 cross-functional members
  • Self-organizing
  • Full-time dedication

Ceremonies

Sprint Planning

  • Backlog item selection
  • Sprint backlog creation
  • 1-16 hour task estimation

Daily Scrum

  • 15-minute standup
  • Three questions:
    • Yesterday's work
    • Today's plan
    • Blockers

Sprint Review

  • Achievement presentation
  • Demo-focused
  • Informal format
  • 2-hour prep limit

Sprint Retrospective

  • Process review
  • 15-30 minutes
  • Team-wide participation

Artifacts

Product Backlog

  • Complete feature list
  • Business value prioritization
  • Product Owner maintained

Sprint Backlog

  • Current sprint tasks
  • Team management
  • Daily updates

Burndown Charts

  • Remaining work visualization
  • Daily tracking
  • Progress monitoring

4. INVEST Criteria for User Stories

  • Independent - Minimal story dependencies
  • Negotiable - Flexible details
  • Valuable - Clear user/customer benefit
  • Estimatable - Effort can be assessed
  • Small - Single sprint scope
  • Testable - Clear completion criteria

5. Scaling Scrum

  • Optimal team size: 7±2 people
  • "Scrum of Scrums" for scaling
  • Suitable for large projects (500+ people)
  • Scaling factors:
    • Application nature
    • Team dimensions
    • Geographical distribution
    • Project timeframe

Exam Tips

Key Focus Areas

  • Three pillars: Roles, Ceremonies, and Artifacts
  • Product vs Sprint Backlog differences
  • Ceremony purposes and procedures
  • INVEST criteria applications
  • Scrum scaling principles