Now everywhere we hear Agile. Around half of all the industries are applying Agile practices. Let’s understand what Agile process is.
Agile is an Iterative and Incremental model where requirements keep on changing. As a company we should be flexible to accept requirements change, develop, test, and finally release a piece of working software within short span of time. The Goal of the agile model is the customer satisfaction by delivering the piece of the software to the customer within short span of time. Agile process follows Agile principles. Now let’s jump in and learn about Agile principles.
There are 12 Agile principles:
1. Customer Satisfaction.
2. Welcome changing requirements.
3. Deliver working software frequently.
4. Work together.
5. Trust Support.
6. Face to Face conversation.
7. Working software.
8. Sustainable development.
9. Technical Excellence.
What is Scrum?
Scrum is a subset of Agile and one of the most popular process frameworks for implementing Agile. It is an iterative software development model used to manage complex software and product development.
Scrum includes group of people called as Scrum team, which are as below:
– 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.
– Dev Team and QA Team
Develop and test the software.
Now time for learning Scrum methodologies.
· User Story: A Feature/module in a software.
· Epic: Collection of user stories.
· Product backlog: Contains list of user stories. Prepared by Product owner.
· Sprint: Period to complete the user stories, decided by the product owner and team, usually 2-4 weeks of time.
· Sprint planning meeting: Meeting conducts within the team to define what can be delivered in the sprint and duration.
· Sprint backlog: List of committed stories by Dev/QA for specific sprint.
· Scrum meeting: Meeting conducted by Scrum Master daily or weekly depends on individual organization, it’s called as Stand up meeting.
· Sprint retrospective meeting: Review meeting after completion of sprint. The entire team, including both the ScrumMaster and the Product owner should participate.
· Story point: Rough estimation of user stories, which will be given by Dev & QA in the form of Fibonacci series.
· Burndown chart: Shows how much work is remaining in the sprint. Maintained by the scrum master daily.
I hope you all have got some sort of understanding on powerful Agile process. Thanks all for your valuable time.