Terms used in Agile:
- Team size in agile varies from five to nine people.
- Team consist of Tester, developer, DBA, support etc. including Product Owner (PO) and Scrum Master.
- As said earlier team is tightly synchronize with each other or we can say they fully synchronized.
- Team size and resource selection depends on sprint duration, Project front end and back end requirement.
- Sprint in agile is nothing but time span or period.
- Usually sprint is of two – four weeks.
- Sprint is the time frame in which task has to be completed and ready for review by end user or work is ready for production deployment.
- Scrum master is key role in agile methodology.
- Scrum master is mediator between PO (Product Owner) and Scrum Team.
- Scrum master is responsible for in time completion of sprint.
- Scrum master keep track of team’s daily activities and responsible for Sprint’s daily progress.
- Scrum master is responsible for resolution of any obstacle that impact on sprints progress, Scrum master communicate with PO for any issue/unclear requirements etc.
- Scrum master organize and monitor Sprint’s daily standup, SM is also participant of daily standup with Product owner.
Business analyst: BA
- Business analyst is the person who knows everything about project and that is why; he is the only point of contact by technical team for any query related to requirements or ambiguity in requirements.
- When requirements are not complete, or ambiguity in requirements then business analyst think over them and try to resolve those issues at own, but if needed he/she can also communicate with Product owner for clarifying issues submitted by technical team on unclear, ambiguity In requirements.
- User stories: Project requirements or features to be implement are call as user stories.
- E.g. Provide functionality for forgot password. This is a feature and is call as one user story.
- Product backlog is the set of all user stories related to product. User stories of Products all features, functionalities collectively called as Product Backlog.
- For each sprint cycle, team including scrum master have sprint planning meeting and discus, review and have brainstorming session on user stories present under product backlog.
- While picking up user stories from product backlog for sprint, different criteria are consider such as priority, dependency and client requirement etc.
- User stories pick from product backlog are the sprint backlog’s user stories.
- As said earlier, user stories from product backlog picked as per priority, dependency on other modules and client requirements.
- Story point is the weightage or in other words complexity of the user story.
- Story points assigned as 1, 2, and 3,5,8,13,21.
- Story points 1, 2, 3 means user story is less complex and efforts require by the team are also less.
- Story points ranging from five, eight means story point is medium complex.
- Story point 13 onwards means user story is highly complex and efforts required are high. In such cases story point may break into small stories.
- User stories assigned based on different parameters such as dependency on other module (whether other module on which it is dependent is ready or need to work), expert level of resources working on this story, whether requirements are clearly specified or not etc.