Agile Methodology

Agile is unlike the traditional software development methodologies. Agile is more on Plan Do Check Act cycle which focuses more on short term development windows called sprints. Due to the constraints of the earlier development methods, Agile paved way for new methods to take shape and the modern day teams observe that no particular method is perfect and truly works as long as the method that a team or a unit adopts provides the desired outcome per the customer requirements, that should is considered. However each process of method has its own framework, processes, rules and regulations.

One of the method is called SCRUM –

SCRUM has the followed time boxed events –

Daily Standup

People involved –

  • Developers, QA, BA, Product Owner

Agenda –

  • What did I work on yesterday?
  • What will I work on today?
  • Roadblocks, issues to move forward

Sprint Review/Demo

People involved –

  • Developers, QA, BA, Product Owner, business stakeholder

Agenda –

  • Developers will one by one demo the stories or task that are complete or done
  • The definition of done OR complete should have been defined during sprint planning session
  • Product owner shall determine along with the business stakeholder about the readiness of the deliverable OR they might take few days to UAT and then provide an update

Sprint Retrospective

People involved –

  • Developers, QA, BA

Agenda –

  • What went really well during the sprint – Continue doing so
  • What didn’t go well – Analyze and improve
  • What should be stopped doing
  • Any other team level impediments or roadblocks, environment challenges, requirement challenges, user story grooming etc.
  • Scrum Master shall facilitate and help the team to work on the reported issues one by one

Sprint Planning

People involved –

  • Developers, QA, BA, Product Owner

Agenda –

  • PO shall come up with priorities of epics or PBIs
  • Entire team shall work on story grooming
  • Entire team shall come up with acceptance criteria
  • Team shall assign points to each user story
  • Based on team velocity of last several sprints, the stories are assigned to a new sprint and locked into a sprint
  • Sprint kickoff