Agile Model / Agile Methodology / Agile Process
It is an Iterative and Incremental Approach.
Agile is an Iterative and Incremental Process
Agile Principles
- Customer no need to wait for long time.
- We develop, test and release piece of software to the customer with few number of features.
- We can accept/accommodate requirement changes.
There will be good communication between customer, Business Analyst, Developer and Testers.
Agile Principles
Agile Advantages
- Requirement changes are allowed in any stage of development, or we can accommodate requirement changes in the middle of development.
- Release will be very fast ( weekly )
- Customer no need to wait for long time.
- Good communication between team.
- It is very easy model to adopt.
Agile Disadvantages
- Less focus on design and documentation since we deliver software very faster
SCRUM & TEAM
Scrum is a framework through which we build software product by following Agile Principles.
Scrum includes group of people called as Scrum team. Normally contains 5-9 members.
- Product Owner
- Scrum Master
- Dev Team
- 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
- The main role is facilitating and driving the agile process.
Developers
- Develop the software.
QA
- Test the software.
Agile Terminology
Scrum Terminology
Sprint Backlog
List of committed stories by DEV/QA for specific sprint.
Sprint/Iteration
Period of time to complete the user stories, decided by the product owner and team, usually 2-4 weeks of time.
Sprint Planning Meeting
Meeting conducts with the team to define what can be delivered in the sprint and duration.
Before the sprint starts a scope is decided in this meeting for the sprint. This is the meeting which finalizes the sprint backlog and sprint goal.
Story Point
Rough estimation of user stories, will be given by Dev & QA in the form of Fibonacci series.
0 1 1 2 3 5 8 …….
1 story point = 1 hour / 1 day ( 6 hours )
Login Page : Dev – 5 QA – 3 = 6 Hours / 1 day
Scrum Meeting ( Daily Standup Meeting )
Meeting conducted by Scrum Master everyday 15 minutes called as Scrum call / Daily Standup Meeting to discuss –
What did you do yesterday ?
What will you do today ?
Are there any impediments in you way?
Sprint Review Meeting
Once the sprint is ended only the completed user stories are delivered. A review meeting is held to approve the deliverables this meeting is termed as a sprint review meeting.
Sprint Retrospective Meeting
Conducts meeting after completion of sprint. The entire team, including both the Scrum Master and Product Owner should participate.
What worked well ?
What didn’t go well or as expected?
What should we try doing next ? ( Learnings )
Burndown chart
Shows how much work remaining in the sprint. Maintained by the scrum master daily.
1 story – 3 days ( 18 Hours )