Scrum – An introduction

One of the most successful agile methods because of its hyper productivity
It is management oriented
Somewhat CMM Level 3 equivalence
Widely Used. Examples:

  • Google Adwords
  • 3M
Scrum Roles
  • Scrum Master (Conducts daily scrum meeting, assure scrum rules are followed, removes obstacles, shields teams, facilitator not a manager)
  • Product Owner(Accountable for product success, defines product features, maintains product backlog)
  • Development team
  • Other parties involved
  • Time Box – 2 to 4 weeks
  • An iteration for a building a piece of increment
  • It’s the working time, not planning or asking what to do
  • the team manages itself during a sprint
  • the team commits to product backlog during sprint planning meeting
  • The Sprint backlog is updated a sprint

Scrum – Agile Methodology – An introduction

  • Agile says “No Documentation”. So, no documents will be created henceforth
  • Each department will transition to Agile methodology in its own pace. Example Testing teams would take a different time to move to agile compared to the development or the project management teams.
  • Start the transition from bottom up. 
  • Ignore story priorities
  • All stories must complete on last 1-2 days of sprint
  • Team should pick up more stories than it can test
  • Make sure Definition of Done (DoD) is never looked into during sprint review and is invisible on team pages too
  • Make sure tasks published on scrum task board do not have test plan review, test execution and bug fixing
  • Code changes should continue till last date of sprint
  • Make sure minimum time exists for bug fixing at the end of sprint
  • Make sure some bugs are carried over to next sprint and to bug backlog
  • Make sure bugs are not tagged to stories/feature
  • Make sure no regression testing is possible in the sprint
  • Focus only on the tasks assigned to you
  • Estimates should include only development complexity/size