Agile crash course

agile.md

Agile model/ Agile methodology / Agile process

It is an iterative and Incremental approch.

Agile Priciples

1. Customer no need to wait for long time
2. We develop, test and release peice of software to the customer with few number of features.
3. we can accept/accomodate requirement changes.

there will be good communication between customer, business analyst, developers and testers.

Advantages

• Requirement changes are allowed in any statge of develpment/ we can accommodate requirement changes in middle of development.

• Release will be very fast

• Customer no need to wait for long time.
• Good communication between team
• very easy model to adopt.

Disadvantage:

Less focus on design and documentation since we deliver software very faster.

Scrum

• Agile is principle, Scrum is a framework through which we build software product by following Agile priciples.

• Scrum, a team involved to delever the product/ group of people, called agile team / scrum team, normally contains 5-9 members.

1. Product owner
2. Scrum master
3. Dev Team
4. QA team

Product Owner

• Define the features of the product
• Prioritize features according to market value
• Adjust features and priority every iteration, as needed
• Accept or Reject work results.

Scrum master

• main role is facilitating and driving the agile process.
• make sure team follow agile process
• from starting to delivering the project, he is responsible and setup all meetings

Scrum Terminology

• User Story : A small feature/module in a software
• Epic: Collection of user stories./ larger requirements, prepared by product owner
• Product backlog : Contains list of user stories. Prepared by product owner
• Sprint : Period of time to complete the user stories, decided by the product owner and team usually 2-4 weeks, also called iteration.
• Sprint Planning meeting : Meeting conducts with the team to define what can be delivered in the sprint and duration.
• Sprint backlog : List of commited stories by Dev/QA for specific sprint. from product backlog we pick stories to be develop in a sprint. (subset of product backlog)
• Scrum meeting : Meeting counducted by Scrum master everyday 15 mins called as scrum call/standup meeting.
  • What did you do yesterday
  • What will you do today
  • Are there any impediments(obstacles) in your way? *
• Spring retrospective meeting : conducts meetings after completion of sprint, the entire team, including both scrum master and product owner should participate.
  • What went well
  • What did not go well
  • What can be improved
• Story point : Rough estimation of user stories, will be given by Dev and QA in the form of fibonacci series. 1 story point = 1 hr / 1 day(6 hours)
  • ex Login --> Dev-5hr, QA-3hr = 8 hours/1 day - 1 story point
• Burndown chart : Show how much work remining in the sprint. Maintained by scrum master daily.
  • 1 story -- 3 Days (18 hr) , but actual 4 Days ,then sprint effects, so scrum master manages a chart to track these.
• Scrum Board : board maintained by team , like Todo, WIP, Testing, done

Defination of Ready(DoR) & Defination of Done (DoD)

Defination of Ready (DoR)	Defination of Done (DoD)
User Story is clear	Code produced( all 'todo' items in code completed)
User Story is testable	Code commented, checked in and run against current version in source control
User Story is Feasible	Peer reviewed, meeting develpment standards
User Story defined	Unit test written and passed
US Acceptance criteria defined	Deployed to system test environment and passed system test
US Dependencies defined	Passed UAT and signed off as meeting requirements
US Sized by develpment team	Any build/deployment/configuration changes are implemented/documented/communicated
Team has idea what it will mean to demo the US	remaning hr for task set to zero and task closed