Ans: Scrum is an agile way to manage a project, usually software development. Agile software development with Scrum is often perceived as a methodology; but rather than viewing Scrum as methodology, think of it as a framework for managing a process.
Ans: Scrum Master Job Descriptions and Responsibilities In Agile Methodology. ...Scrum master is a challenging role and needs to understood according to priority set by the product owner. Scrum Master must execute the backlog as wished by product owner, making sure that deliverables are on time with production quality.
Ans: The major differences are:
Ans: The candidate should understand that there is no way to ensure access to stakeholders. All that can be done is to encourage stakeholders to engage in meaningful communication by being transparent and helpful. Sprint demos are a useful mechanism for this, often promoting better relationships between different departments and business units — improving a scrum team’s access to their projects’ stakeholders.
Ans: Scrum is a type of iterative model only but it is iterative + incremental.
Ans: Writing user stories should be a joint effort made by the entire scrum team. If it's not, the team might not feel that they have ownership of the stories — inevitably leading to less or no buy-in, reduced motivation… and ultimately a lower-quality product.
Ans: There are 3 major ceremonies performed in Scrum:-
Ans: We discuss three things:-
Ans: There are two artifacts maintained in Scrum:
Ans: It’s measured by Velocity.
Ans: Velocity is the sum of story points that a scrum team completes (meets the definition of done) over a sprint.
Ans: Complexity and effort is measured through “Story Points”. In scrum it’s recommended to use Fibonacci series to represent it.
Ans: The progress is tracked by a “Burn-Down chart”.
Ans: Burn down chart is a graph which shows the estimated v/s actual effort of the scrum tasks.
It is a tracking mechanism by which for a particular sprint; day to day tasks are tracked to check whether the stories are progressing towards the completion of the committed story points or not. Here we should remember that the efforts are measured in terms of user stories and not hours.
Ans: During Sprint review we walk through and demonstrate the feature or story implemented by the scrum team to the stake holders.
During retrospective, we try to identify in a collaborative way what went well, what could be done better and action items to have continuous improvement.
Ans: A good user story:
Ans: Assigning tasks to individual team members does not work at all and needs to be stopped. The assignment of user stories is the scrum team’s prerogative. Preventing individual task assignment, if likely to occur, should be one of the Scrum Master’s most pressing concerns
Ans: Automation plays a vital role in Scrum. In order to have continuous feedback and ensure a quality deliverable we should try to implement TDD, BDD and ATDD approach during our development. Automation in scrum is not only related to testing but it is for all aspect of software development. As I said before introducing TDD, BDD and ATDD will speed up our development process along with maintaining the quality standards; automating the build and deployment process will also speed up the feature availability in different environment – QA to production. As far as testing is concerned, regression testing should be the one that will have most attention. With progress of every sprint, the regression suit keeps on increasing and it becomes practically very challenging to execute the regression suit manually for every sprint. Because we have the sprint duration of 2 – 4 weeks, automating it would be imperial.
Ans: We have the Product backlog refinement meeting (backlog grooming meeting) where the team, scrum master and product owner meets to understand the business requirements, splits it into user stories, and estimating it.
Ans: DoD stands for Definition of done. It is achieved when
Ans: A Minimum Viable Product is a product which has just the bare minimum required feature which can be demonstrated to the stakeholders and is eligible to be shipped to production.
Ans: Epics are equivocal user stories or we can say these are the user stories which are not defined and are kept for future sprints.
Ans: A Story point is calculated by taking into the consideration the development effort+ testing effort + resolving dependencies and other factors that would require to complete a story.
Ans: Yes, this is a very common scenario. There may be a chance that the story point given by the development team is, say 3 but the tester gives it 5. In that case both the developer and tester have to justify their story point, have discussion in the meeting and collaborate to conclude a common story point.
Ans: In ideal case, the requirement becomes a story and moves to the backlog. Then based on the priority, team can take it up in the next sprint. But if the priority of the requirement is really high, then the team will have to accommodate it in the sprint but it has to very well communicated to the stakeholder that incorporating a story in the middle of the sprint may result in spilling over few stories to the next sprint.
Ans: A story is done only when it is development complete + QA complete + acceptance criteria is met + it is eligible to be shipped into production. In this case if there are defects, the story is partially done and not completely done, so I will spill it over to next sprint.