introduction to agile scrum methodology
DESCRIPTION
This is a presentation for software developers and testers to understand and start working on the very famous Agile SCRUM methodology for software development and testingTRANSCRIPT
INTRODUCTION TO SCRUM
Sprint Pre-planning:
• Identification of what stories will be worked on during the sprint
• Move stories from product backlog into the sprint backlog
Sprint Kick - Off
• Review the stories in the sprint backlog
• Select a few stories and start to task out the sub-tasks to complete the stories
Story Tasking:
• Before you start a story, please ensure that we have created the appropriate sub-tasks (as best we can ... sub-tasks can be
• added/deleted as we work on the story)
• Please ensure the following sub-tasks are a part of the story: Jira Ticket Lifecycle
• Please ensure that the sub-tasks have the appropriate release and sprint numbers assigned to them
Working on the story:
• If story work has started, please move the story to "Dev in Progress“
• Please ensure that the sub-task status is up-to-date ...
• If you're working on a sub-task it should be "Dev in Progress“
• If you've completed a sub-task it should be "Dev Complete" and re-assigned to your QA counterpart
• If you're working on verifying the sub-task work, it should be "QA in Progress“
• If you've completed the verification of the sub-task, it should be closed and marked as "Done"
Closing a story:
• Once all the tasks associated with the story have been completed, the story needs to be marked as closed.
RetrospectiveWHAT WENT GOOD WHAT WENT BAD
IMPROVEMENTS
Scrum of Scrum meeting
• just like the daily standup or daily scrum. He also suggests timeboxing the meetings to last no more than fifteen minutes.
REVANTH REDDY AIRRE (RAR)
CAST INDIA