- Report this article
Isha Jajoo
Isha Jajoo
Senior Test Automation Engineer @EPAM
Published Mar 1, 2017
+ Follow
Hi guys,
I have been part of Agile methodology since 6 months, so I would like to share my experience and the terms associated with Agile:
So first question is:
What is Agile ?
Agile is a time-boxed iterative approach where making changes in requirement is easy and can be made in the mid of the Software Development Lifecycle. Here the functionalities are broken down into small user stories. On the basis of their priorities, they are taken into a particular sprint. So next term in agile is Sprint.
What is Sprint ?
Release of a product is broken into sprints. For eg: If a release is of 2 months, then it has 3-4 sprints. 1 Sprint usually last for 15 days.
First sprint is usually of small time, so small stories are taken up in it. Then more stories can be taken up depending on the priorities and the sprint time. There will be levels of testing in Sprints also, as in there are 'n' sprints, so first 'n-1' sprints will be part of Integration phase and 'nth' sprint will be part of System Integration Testing phase.
Next part of Agile is who all are the members of an Agile team:
- Scrum Master(SM): Facilitates the Agile process and lead all the meetings. Makes sure there is no communication gap amongst the team members. And resolve impediments, if any.
- Product Owner(PO): One who has knowledge and experience of the overall product is designated as PO. He/She clarifies any doubt related to the requirement with the business and convey that to the team.
- Developers : All other members in the team whether they are testers, BA or developers are designated as developers. They work collectively and deliver the requirement.
Another important part of Agile is Meetings and discussions.
There are many meetings so that there is no doubt of the requirement and transparency is maintained between the client and the team. Meetings like :
- Backlog refinement : Discussion about the stories to be taken in next sprint and if any inputs are needed from the client.
- Stand up meeting : Daily status meeting of 15 mins where every team member give their statuses including what is currently going on, what happened yesterday, what we are planning to do and also if any impediments or issues faced.
- Sprint review: In this , demos of all the requirements is given and if the PO approves the demo, it is marked as done.
- Sprint retrospective: Here , we discuss what went good, what went wrong, improvement areas .
- Sprint planning : Here Sprint name, availability of the team members in %, stories to be taken and their story points are all discussed with the whole team.
The most important part of Agile is communication. There should be transparency throughout the sprint and if there is any bug( called as observation during integration phase), then that is logged.
Like
Celebrate
Support
Love
Insightful
Funny
49
8 Comments
David Comfort
IT Control, Bank of Industry Limited
6mo
- Report this comment
😍 I love this very simple explanation. I can now relate it to what my lecturer was saying. Thanks for sharing
1Reaction
Sreeneewasan Krishnan, CSPO®, PRINCE2, LSSGB
Project Manager at HERE Technologies
3y
- Report this comment
Indeed simple and informative
1Reaction
Reddy Prasad
Project Manager | CSM | Pharma & Healthcare
3y
- Report this comment
Thanks Isha
1Reaction
Abhay Kumar Singh
Looking for Freelance Opportunity | Quality Assurance Engineer | Proud Manual Tester | Scrum Master | Agile & SaFe Practitioner | API Testing | DB Testing | Mobile Testing |Speaker | Insurance| Healthcare | ECommerce
5y
- Report this comment
Good one
1Reaction
Jayesh Gopalan
Operations / Project Specialist
5y
- Report this comment
Good. Thanks
1Reaction
See more comments
To view or add a comment, sign in
More articles by this author
No more previous content
- Golden rules to Break the change chain Nov 26, 2019
- Ace body language basics Sep 19, 2019
No more next content
Sign in
Stay updated on your professional world
Sign in
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Insights from the community
- Agile Methodologies How can you adjust your sprint or flow cycle when the scope changes?
- Agile Methodologies How do you fix Agile sprint defects?
- Program Management How can you manage dependencies and constraints in agile user stories?
- Agile Methodologies How can you clarify unclear or poorly defined product backlog items?
- Software Project Management How can you make agile quality assurance and testing practices transparent to all stakeholders?
- Agile Methodologies What is the scrum master's role in managing user story dependencies?
- Agile Methodologies What is a sprint backlog and how does it support Agile methodologies?
- Agile Methodologies What are the best practices for mitigating risk in user stories?
- Agile Methodologies What is the Scrum of Scrums and how does it help manage large-scale Agile projects?
- Agile Methodologies How can you balance Agile principles with quality assurance?
Explore topics
- Sales
- Marketing
- IT Services
- Business Administration
- HR Management
- Engineering
- Soft Skills
- See All