SlideShare a Scribd company logo

Agile_basics

•
•
Mithilesh Singh
Mithilesh Singh

Basics of Agile for beginners. It will help you to understand what is agile and what are all terminologies we use in Agile.

Related slideshows

Manual Testing Material by Durgasoft
Manual Testing Material by DurgasoftManual Testing Material by Durgasoft
Manual Testing Material by Durgasoft
 
Severity and Priority
Severity and PrioritySeverity and Priority
Severity and Priority
 
Introduction to Agile Testing
Introduction to Agile TestingIntroduction to Agile Testing
Introduction to Agile Testing
 
1 of 27
By Mithilesh Singh
Scrum
What is Agile? Agile is a methodology or process which follows the Iterative and Incremental Approach. Iterative means same kind of steps getting repeated again and again in every sprint cycle. E.g. requirement analysis -- > designing --> coding --> testing. Incremental Approach means we will be adding the developed features in every sprints and integrating with older features.
Agile Key Principles We can deliver active product in short period of time. So customer can start using it in the very beginning. We handover the product to customer with lesser no of features at first and then start adding the features sprint basis. In between requirement changes are acceptable.
Advantages ? We can have frequent changes in between the development process, it is allowed. Customer involvement will be there from the beginning. Fast release of the product. Good collaborationbetween teams[Dev, QA, team leads, Manager] Customized approach for the company.
Disadvantages Documentation could get lengthy. It is not useful for small projects. It required expert persons to take important decisions in the meeting. Cost more as compare to waterfall model.
AgileSoftware development framework
What is Scrum & Scrum Team Scrum: It is a framework, we follow this framework in agile process to build the product.We have XP,Kanbanalso for agile development There are multiple team involves in the agile process called as Agile team or scrum team. Agileteam = Product owner + Scrum master + Dev team + QA team. Overall members contain in the scrum team is 5 – 9.
1. Product owner role: • Product owner is someone who will have complete clarity on the product which is going to develop, • all the features and sub features list would be along with him/her. • owner can prioritize the feature and accordingly can fix that in development iteration. • Product owner can also deprioritize any feature and remove from the development cycle as per market situation. • Development team have to show or demo the development feature to the Product owner. • Product owner also responsible to communicatewith marketing and sales team to see the product value in the market.
2. Scrum Master role: • Scrum master helps to drive the agile process in the company, • Scrum master handles the agile process related queries and solve bottlenecks arises in the process. • He acts as bridge between product owner and the other teams.
3. Dev + Testing role: • Development: • Dev team will responsible to developthe feature using specific programming language and predefined framework and deliver it to tester for testing. • Dev also responsibleto perform unit testing(White box testing]. • Testers will take the build and test the feature as per the requirement and give the sign off if everything works as expected.
Scrum Terminologies comparison – Agile vs Model
Scrum Terminologies
Epic • Collection of more than one user stories and Task
User Story • User Story represents a module or feature of a software. • It is collection of multiple tasks. • Each task will indicate th e effort given to develop the product
Product Backlog • Product Backlog is the collection of the user stories which will being developed upcoming sprints, Product owner is responsible to create these stories and keep it as product backlog. Note: Epic is also collection of stories but those will be the part of any sprint. So we can call it as sprint backlog. But in case of product backlog it contains all the requirements for upcoming development.
Sprint • It defines as a period of time to complete the allocated tasks or stories. • We keep sprint duration usually 2-4 weeks.
Sprint Planning • Sprint planning meeting happens in the beginning or before starting any sprint to decide what to pick and deliver to client in this sprint and what should be the duration. • Product owner, Scrum master, Developer and Testers use to involve in this meeting.
Sprint Review • Sprint Review meeting conductsin between any running sprint to get the answer to following questions mentioned in the screenshot.
Sprint Backlog • After sprint planning meeting once we decide to pick the stories from the product backlog, we pick those stories and keep under current sprint those stories are nothing but sprint backlog. In general list of stories we are going to cover in the current sprint.
Scrum meeting • This is a meeting conducted by scrum master everyday morning for short duration like 15 mins, this is also called as stand up meeting. Why this is called so because this is very small duration meeting, people use to stand in a circle with team and quickly start discussing on below points and complete it withing 15 mins. A. What did you do yesterday? B. What will you do today? C. Are there any blockers in your way?
Agile_basics
Story point • It is the Rough estimation of user stories. • Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product
Burndown chart • A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. • The burndown is a chart that shows how quickly you and your team are burning through your customer's user stories. • Burndown charts graphically illustrate how fast your team is working by plotting user stories againsttime.
Scrum Board: This is something to give the overall work progress in the sprint like how many tasks have been completed, how manyin progress, how much is done so based on this we can plane about remaining tasks. To manage this board we have tools which provide this kind of board e.g. Jira, Rally etc.
What tasksQA and Dev performs in everystory?
Agile_basics

More Related Content

Agile_basics

  • 3. What is Agile? Agile is a methodology or process which follows the Iterative and Incremental Approach. Iterative means same kind of steps getting repeated again and again in every sprint cycle. E.g. requirement analysis -- > designing --> coding --> testing. Incremental Approach means we will be adding the developed features in every sprints and integrating with older features.
  • 4. Agile Key Principles We can deliver active product in short period of time. So customer can start using it in the very beginning. We handover the product to customer with lesser no of features at first and then start adding the features sprint basis. In between requirement changes are acceptable.
  • 5. Advantages ? We can have frequent changes in between the development process, it is allowed. Customer involvement will be there from the beginning. Fast release of the product. Good collaborationbetween teams[Dev, QA, team leads, Manager] Customized approach for the company.
  • 6. Disadvantages Documentation could get lengthy. It is not useful for small projects. It required expert persons to take important decisions in the meeting. Cost more as compare to waterfall model.
  • 8. What is Scrum & Scrum Team Scrum: It is a framework, we follow this framework in agile process to build the product.We have XP,Kanbanalso for agile development There are multiple team involves in the agile process called as Agile team or scrum team. Agileteam = Product owner + Scrum master + Dev team + QA team. Overall members contain in the scrum team is 5 – 9.
  • 9. 1. Product owner role: • Product owner is someone who will have complete clarity on the product which is going to develop, • all the features and sub features list would be along with him/her. • owner can prioritize the feature and accordingly can fix that in development iteration. • Product owner can also deprioritize any feature and remove from the development cycle as per market situation. • Development team have to show or demo the development feature to the Product owner. • Product owner also responsible to communicatewith marketing and sales team to see the product value in the market.
  • 10. 2. Scrum Master role: • Scrum master helps to drive the agile process in the company, • Scrum master handles the agile process related queries and solve bottlenecks arises in the process. • He acts as bridge between product owner and the other teams.
  • 11. 3. Dev + Testing role: • Development: • Dev team will responsible to developthe feature using specific programming language and predefined framework and deliver it to tester for testing. • Dev also responsibleto perform unit testing(White box testing]. • Testers will take the build and test the feature as per the requirement and give the sign off if everything works as expected.
  • 14. Epic • Collection of more than one user stories and Task
  • 15. User Story • User Story represents a module or feature of a software. • It is collection of multiple tasks. • Each task will indicate th e effort given to develop the product
  • 16. Product Backlog • Product Backlog is the collection of the user stories which will being developed upcoming sprints, Product owner is responsible to create these stories and keep it as product backlog. Note: Epic is also collection of stories but those will be the part of any sprint. So we can call it as sprint backlog. But in case of product backlog it contains all the requirements for upcoming development.
  • 17. Sprint • It defines as a period of time to complete the allocated tasks or stories. • We keep sprint duration usually 2-4 weeks.
  • 18. Sprint Planning • Sprint planning meeting happens in the beginning or before starting any sprint to decide what to pick and deliver to client in this sprint and what should be the duration. • Product owner, Scrum master, Developer and Testers use to involve in this meeting.
  • 19. Sprint Review • Sprint Review meeting conductsin between any running sprint to get the answer to following questions mentioned in the screenshot.
  • 20. Sprint Backlog • After sprint planning meeting once we decide to pick the stories from the product backlog, we pick those stories and keep under current sprint those stories are nothing but sprint backlog. In general list of stories we are going to cover in the current sprint.
  • 21. Scrum meeting • This is a meeting conducted by scrum master everyday morning for short duration like 15 mins, this is also called as stand up meeting. Why this is called so because this is very small duration meeting, people use to stand in a circle with team and quickly start discussing on below points and complete it withing 15 mins. A. What did you do yesterday? B. What will you do today? C. Are there any blockers in your way?
  • 23. Story point • It is the Rough estimation of user stories. • Story points are a unit of measure for expressing an estimate of the overall effort that will be required to fully implement a product
  • 24. Burndown chart • A burndown chart shows the amount of work that has been completed in an epic or sprint, and the total work remaining. • The burndown is a chart that shows how quickly you and your team are burning through your customer's user stories. • Burndown charts graphically illustrate how fast your team is working by plotting user stories againsttime.
  • 25. Scrum Board: This is something to give the overall work progress in the sprint like how many tasks have been completed, how manyin progress, how much is done so based on this we can plane about remaining tasks. To manage this board we have tools which provide this kind of board e.g. Jira, Rally etc.
  • 26. What tasksQA and Dev performs in everystory?