- What is Velocity?
- What do you know about impediments in Scrum? Give some examples of impediments.
- What is the difference and similarity between Agile and Scrum?
- What is the increment? Explain.
- What is the “build-breaker”?
- What is a User Story?
- What do you understand by Daily Stand-Up?
- What do you know about Scrum ban?
- How is Agile Methodology different than Traditional Waterfall process?
- Difference between extreme programming and scrum?
- What is Kanban?
- What are burndown and burn-up charts in agile methodology?
- According to you what are some qualities that a good agile tester must have?
- State some of the Agile quality strategies.
- What are MVP and MMP?
- Do you know about Agile Manifesto & its Principles? Explain in brief.
- Is there any drawback of the Agile model? If yes, explain.
- What is the use of burn-up and burn-down charts?
- Define Zero Sprint and Spike in Agile.
- What is the role of the Scrum Master?
- What do you know about a story point in Scrum?
- What is the role of Sashimi in Scrum methodology?
- What are the different roles in Scrum?
- What are the responsibilities of a Scrum Master?
- What are different ceremonies and their importance in Scrum?
- What do you understand by the term Agile testing?
- State some major principles of Agile testing.
- What are the skills of a good Agile Tester?
- What do you understand by the term “Scrum of Scrums”?
- Scrum is an Agile framework, right? Name a few other Agile frameworks.
- Explain some common metrics for Agile.
- Is it ever suggested to use waterfall over Scrum? If yes, explain when.
- Why does Scrum encourage the use of automated testing for projects?
- What do you know about “Planning Poker” technique?
- Name some methodologies and development where you have used the Agile model.
- What is the difference between the agile & traditional way of working?
- What is the difference between Sprint Planning Meeting and Sprint Retrospective Meeting?
- How is an agile testing methodology different from other testing methodologies?
- When can you say your story is ready to develop/groom enough to deliver?
- Can you explain the lean methodology in detail?
- Is there any difference between incremental and iterative development?
- Can you explain pair programming and its benefits?
- Mention the principles of Agile testing.
- What is an agile manifesto and its principle?
- Is it ever suggested to use waterfall over Scrum? If yes, explain when.
- What is an epic, user stories and task?
- Explain what is re-factoring?
- Explain how you can measure the velocity of the sprint with varying team capacity?
- Mention the key difference between sprint backlog and product backlog?
- What is test driven development?
- Prototypes and Wireframes are widely used as part of?
- What is story points/efforts/ scales?
- Explain what is tracer bullet?
- What is a test stub?
- Mention what are the Tools that can be useful for screenshots while working on Agile projects?
- Explain how can you implement scrum in an easy way to your project?
- Explain what does it mean by product roadmap?
- Is canceling a Sprint possible? Who can cancel a Sprint?
- What are the primary tools used in a Scrum project?
- What do you mean by release candidate?
- Define the roles in Scrum?
- What is Sprint 0 and Spike?
- What is User-Story Mapping?
- How to deal with Score Creep?
- What does DoD mean?
- How can a Scrum Master be a Servant Leader?
Velocity question is generally posed to understand if you have done some real work and familiar with the term. Its definition “Velocity is the rate at which team progresses print by sprint” should be enough. You can also add saying the important feature of velocity that it can’t be compared to two different scrum teams.
Impediments are the obstacles or issues faced by scrum team which slow down their speed of work. If something is trying to block the scrum team from their getting work “Done” then it is an impediment. Impediments can come in any form. Some of the impediments are given as –
- Resource missing or sick team member
- Technical, operational, organizational problems
- Lack of management supportive system
- Business problems
- External issues such as weather, war etc
- Lack of skill or knowledge
While answering impediments related agile scrum interview questions remember that you may be asked the way to remove any of the mentioned impediment.
Difference between Agile and Scrum – Agile is a broad spectrum, it is a methodology used for project management while Scrum is just a form of the Agile that describes the process and its steps more concisely. Agile is a practice whereas scrum is a procedure to pursue this practice.
The similarity between Agile and Scrum – The Agile involves completing projects in steps or incrementally. The Agile methodology is considered to be iterative in nature. Being a form of Agile, Scrum is same as that of the Agile. It is also incremental and iterative.
An increment is the total of all the product backlogs items completed during a sprint. Each increment includes all the previous sprint increment values as it is cumulative. It must be in the available mode in the subsequent release as it is a step to reach your goal.
The build-breaker is a situation that arises when there is a bug in the software. Due to this sudden unexpected bug, compilation process stops or execution fails or a warning is generated. The responsibility of the tester is then to get the software back to the normal working stage removing the bug.
- A user story is an agile software development/ project management tool that provides teams with simple, natural language explanations of one or more features of the project that’s written from the perspective of the end-user.
- The user story doesn’t go into detail but only mentions how certain types of work will bring value to the end-user. The end-user, in this case, could be an external component or an internal customer/colleague within the organization.
- They also form the building block of agile frameworks like epics and other initiatives.
- They ensure that the teams work towards the goals of the organization, with the help of epics and initiatives.
- The requirements to make a user story a reality are added later, after discussions with the team.
- They are recorded on post-it notes, index cards, or project management software.
You may surely get an interview question about daily stand-up. So, what should be the answer to this question? The daily stand-up is an everyday meeting (most preferably held in the morning) in which the whole team meets for almost 15 minutes to find answer to the following three questions –
- What was done yesterday?
- What is your plan for today?
- Is there any impediment or block that restricts you from completing your task?
The daily stand-up is an effective way to motivate the team and make them set a goal for the day.
Scrum-ban is a Scrum and Kanban-based model for the software development. This model is specifically used for the projects that need continuous maintenance, have various programming errors or have some sudden changes. This model promotes the completion of a project in minimum time for a programming error or user story.
This is the most commonly asked agile interview question. In agile methodology, features of the software are delivered frequently, so that the testing activity is done simultaneously with the development activity. Testing time is shortened as only small features are need be tasted at once.
While, in the waterfall model, testing activities take place at the end of the entire development process. Testing time, in this case, is as long as the entire product is to be tested in one go. Waterfall methodology is a closed process where all stakeholders are not involved in the development process whereas agile methodology requires the involvement of various stakeholders including customers.
Scrum teams usually have to work in iterations which are known as sprints which generally last up to two weeks to one month long while XP team works in the iteration that lasts for one or two weeks.
XP teams are more flexible as they can change their iterations while Scrum teams do not allow any change in their iterations.
The product owner prioritizes the product backlog but the team decides the sequence in which they will develop the backlog items in scrum methodology. Whereas XP team works in strict priority order, features developed are prioritized by the customers.
Kanban is a tool which helps the team to keep a close eye the work i.e., to measure its progress. Apart from the progress, the status of a development story can be seamlessly described with the help of ‘kanban board’. Kanban board aids in writing the whole scenario of a project at a single place to give a perfect picture of the bottleneck, a task done, workflow progress. It helps in the continuous delivery of the product without overburdening the team.
To track the progress of an ongoing project, these charts are used. Burn-up charts indicate the work that has been completed while Burn-down chart shows the amount of remaining work in a project.
A competent agile tester must possess the following qualities:
- They should be capable of understanding the requirements quickly.
- An agile tester should be aware of all the agile principles and concepts and values as listed down in an agile manifesto.
- They should be able to prioritize the work based on the requirements.
- They should have excellent communication skills as continuous communication between business associates, developers and tester is a backbone of the agile development process.
Some of the Agile quality strategies are –
- Dynamic code analysis
- Short feedback cycles
- Reviews and inspection
- Standards and guidelines
- Milestone reviews
Minimum viable product (MVP) is a Lean Startup concept that stresses the impact of learning while performing product development. This allows one to test and understand the idea by getting exposed to the initial version for target customers & users. To accomplish this, one has to collect all the relevant data and learn from that collected data. The thought behind MVP is to produce the product, to provide access to the users, and to observe how the product is used, perceived, and understood. This will also provide more insight towards what the customers’ or users’ needs are.
The MMP (Minimal Marketable Product) refers to the description of the product, which will have a minimal number of features that address the requirement of the users. The MMP would help also help the organization reduce the time to market
This is the theory which most of agile/scrum roles aspirant should be on tips. Four manifesto values and 12 principles should be explained as much as possible as part of this question. Even if it’s not explained in 100% accurate manner it should be fine but intentions of values and principles should come out e.g.
- Working Software should be demonstrated at regular intervals
- Individuals & interaction – self-organization, self-motivating should be encouraged
- Customer collaboration
- Welcoming change at any point in time in the project
Yes, there are some drawbacks of the Agile model, some of them are as follows –
- It is not easy to make a prediction about the effort required to complete a task.
- It becomes more problematic in case of large projects as it becomes difficult to get an idea of the total effort required.
- At sometimes, it’s not possible to properly focus on the design and documentation of the project
- In case the requirements of the client are not understood properly, the final project will not meet the customer requirements. Thus, it will lead to the customer dissatisfaction.
Only the leader who has considerable experience in Agile methodologies is capable to take important decisions. The team members with little or no experience are not involved in decision-making, thus they don’t get chance to advance their knowledge. It’s not always the case that you will be asked the questions about the characteristics and advantages of the agile and scrum in an agile scrum interview. So, just prepare yourself for the drawbacks and disadvantages related agile scrum interview questions.
The burn-up chart illustrates the amount of completed work in a project whereas the burn-down chart depicts the amount of work remained to complete a project. Thus, the burn-up and burn-down charts are used to trace the progress of a project.
Zero sprint – Zero Sprint can be defined as the preparation step of the first sprint in Agile. There are some activities that are required to be done before actually starting the project. These activities are considered as the Zero sprint; the examples of such activities are – setting the environment for development, preparation of backlogs etc.
Spike – Spike is the type of story that can be taken between the sprints. Spikes are commonly used for the activities related to the design or technical issues such as research, design, prototyping, and exploration. There are two types of spikes – functional spikes and technical spikes.
The scrum master is the leader as well as coach of the Scrum team. The scrum master is responsible to serve and protect his team from any kind of distractions that could affect their performance. The main role of the scrum master is to motivate his team to achieve the sprint goal. He is focused to build a self-organized and motivated team where each member is familiar with the implementation of Agile and Scrum principles and applications. The scrum master keeps a proper check on the scrum team if they are executing committed tasks properly. He is also responsible to increase the efficiency and productivity of the team so that they can achieve the sprint goal effectively.
A story point in Scrum is the unit for the estimation of total efforts that are required to perform or complete a particular task. So, here is how you can answer such agile scrum interview questions on a single line.
Sashimi plays an important role in Scrum methodology. Sashimi is a technique used by Scrum to check the completion of all the functions created by the developers. Using this technique, all the requirements such as analysis, designing, coding, testing and documentation that are used in the constitution of a product are checked and only after that the product is displayed.
The three scrum roles i.e. Scrum Master, Product Owner and Team should be explained with the details of few primary responsibilities of each role. You can add more details as mentioned below for a particular depending on the role you are getting interviewed for.
Product owner – A product owner is actually the stakeholder of the project. He represents the project requirements before the team. He is responsible to have a vision of what to build and convey his detailed vision to the team. He is the starting point of an agile scrum software development project.
Scrum team – Scrum team is formed by the collective contribution of individuals who perform for the accomplishment of a particular project. The team is bound to work for the timely delivery of the requested product.
Scrum master – Scrum master is the leader and the coach for the scrum team who checks whether the scrum team is executing committed tasks properly. He is also responsible to increase the efficiency and productivity of the team so that they can achieve the sprint goal effectively.
Key responsibilities of a Scrum Master involves:
- Tracking and monitoring
- Understanding requirements properly
- Work to reach the project goal
- Process checking master and quality master
- Protect the team from detachments
- Improving the performance of the team
- Lead the meetings and resolve issues
- Resolution of conflicts and impediments
- Communication and reporting
Scrum planning, Scrum – Daily stand up, Scrum review & scrum retrospective ceremonies should be clearly expressed with the purpose of the ceremony. It’s important to remember the time-boxing of the ceremonies for a standard 4 weeks of Sprint or as per the Sprint you have used in your projects.
Agile testing is a software testing practice that is fully based on the agile principles of software development. It is an iterative methodology where the requirements are the outcome of collaboration between the product owner and team. The agile principles and applications are applied to meet the customer requirements by successful completion of the project.
Some major principles of Agile testing are –
- Customer satisfaction
- Face to face communication
- Sustainable development
- Quick respond to changes
- Continuous feedback
- Successive improvement
- Focus on essence
- Error-free clean node
- Collective work
An agile tester is one who implements agile software development principles for software testing. Followings are the skills of a good agile tester –
- Required to be familiar with the concepts and principles of Agile
- Should have an excellent communication to communicate with the team and the clients
- Ability to set priority for the tasks according to the requirements
- Should be able to understand the requirements properly
- Understanding of the risks involved with a project due to changing requirements
This is one of the commonly asked scrum master interview questions. Consider a case to understand the meaning of the term scrum of the scrums. Let us assume an active project on which seven teams are currently working. The number of members of each team is also seven. Each team is responsible to lead its own scrum meeting. But, in order to coordinate and communicate with different teams, it is required to organize a separate scrum meeting. The scrum meeting organized to hold a coordination between scrum teams is known as the scrum of scrums. There is one team leader from every team, known as ambassador, who is responsible to represent his team in the scrum of scrums.
Yes, Scrum is an Agile framework. Few other Agile frameworks are –
- Feature Driven Development
- Test Driven Development
While answering this type of Agile Scrum interview questions please note that name the frameworks you are familiar with or have followed.
You may definitely come across agile scrum interview questions regarding agile metrics. The question may be related to a particular agile matric or explaining all the metrics. So, the detailed description of some common metrics for Agile is as follows:
Velocity – Velocity is the average number of points from last 3-4 sprints. It is measured by the summation of the all approved estimates of the stories. It gives an idea of the capacity, progress etc.
Cumulative Flow Diagram – With the help of a cumulative flow diagram, an inspection is done over the uniform workflow. In this diagram/graph, the x-axis represents time whereas the y-axis represents the number of efforts.
Work Category Allocation – Work category allocation is an important factor that gives a quick information of the time investment i.e. where the time is being invested and which task should be given priority as a factor of time.
Time Coverage – It is the time that is given to a code during testing. It is calculated in percentage as a factor of the number of lines of code called by the test suite and the total number of relative lines of code.
Business Value Delivered – It is a term which denotes the working efficiency of the team. The business objectives are assigned numerical values 1,2,3.. and so on, as per the level of priority, complexity, and ROI.
Defect Removal Awareness – It is the factor that helps the team to deliver a quality product. The identification of an active number of defects, their awareness, and removal plays an important role in delivering a high-quality product.
Defect Resolution Time – It is a procedure through which the team members detect the defects (bugs) and set a priority for the defect resolution. The procedure of fixing errors/bugs or defect resolution comprises of multiple processes such as clearing the picture of defect, schedule defect fixation, completing defect fixation, generation, and handling of resolution report.
Sprint Burn Down Matric – The sprint burndown chart is a graph to represent the number of non-implemented or implemented sprints during as Scrum cycle. This matric helps to track the work completed with the sprint.
Yes, sometimes it is suggested to use a waterfall model over Scrum. It is done when the customer requirements are simple, well-defined, fully understood, predictable, and are not subjected to change until the completion of the project. It may the case that you would haven’t ever used waterfall over Scrum but you need to prepare for such Agile Scrum interview questions.
Scrum encourages the use of automated (automated performance or automated regression) testing to make the fastest possible delivery of the project. While answering this question, you may explain some tools that you have used for automated testing.
Planning poker, also known as Scrum Poker, is a card-based agile technique that is used for planning and estimation. To start a session of planning poker technique, the agile user story is read by the product owner. The steps performed in the poker planning technique are –
- Each estimator has a deck of poker cards with the values such as 0, 1, 2, 3, 5, and so on, to denote story points, ideal days or something else that the team uses for estimation.
- Each estimator has a discussion with the product owner and then privately selects a card on the basis of their independent estimation.
- If the cards with same value are selected by all estimators, it is considered as an estimate. If not, the estimator discusses the high and low value of their estimates.
- Then again, each estimator privately selects a card and reveals. This process of poker planning is repeated to reach a general agreement.
While answering this type of agile scrum interview questions, keep in mind to mention those methodologies that are familiar with. Some of the methodologies and development where the Agile model can be used are –
- Crystal methodologies
- Lean software development
- Dynamic development
- Feature-driven development
This question is to judge whether one is aware of the environment of the agile way of working. Here the answer is expected to cover few or all of below:
- The traditional way is sequential where design->Development->Testing etc. happens one after another whereas in agile all of this is done in every iteration/sprint.
- Changes are welcomed in agile as Scope is flexible whereas in traditional manner scope is fixed in the beginning due to which changes have to follow change request path.
- Progress is measured with % completion traditionally whereas working software is the measure of progress in agile.
- Project Manager as a central controlling authority is traditionally driving the project whereas Self-motivated and self-organizing teams drive the projects in agile.
The difference between Sprint Planning Meeting and Sprint Retrospective Meeting is as follows:
Sprint Planning Meeting – A meeting in which all the Scrum roles (product owner, scrum team, and scrum master) have a discussion about the team’s priority features and product backlog items is known as sprint planning meeting. This meeting is held every week and lasts for almost 1 hour.
Sprint Retrospective Meeting – A meeting in which all the Scrum roles (product owner, scrum team, and scrum master) have a discussion about the good part of the sprint, the bad part of the sprint, and the sprint improvements is known as sprint retrospective meeting. This meeting that is held at the sprint review meeting or at the end of the sprint; it lasts for 2-3 hours.
This is one of the frequently asked Agile Scrum interview questions. You may be asked to define the above terms separately or the difference between these two.
Agile scrum interview questions may include a number of questions from agile testing. Let’s understand how you can answer such questions.
The agile testing methodology involves the division of the whole testing process into multiple small segments of codes. In every step, these segments of codes undergo testing. There are a number of additional processes involved in agile testing methodologies such as team communication, strategic modifications for optimal results and many others.
Ready is a stable state of Scrum that is linked to a user story. As per the Definition of Ready (DoR), a user story have to satisfy some conditions before picking it up for a sprint i.e. to be in the ready state. So, the conditions that are essential for the development/grooming of a user story specify if the user story is ready to develop/groom enough to deliver or not.
Basically, the following questions should be answered to consider a user story ready:
Why: Is it clear what the business or stakeholders are trying to achieve?
What: Is the goal or outcome of the user story clear?
How: Is the strategy for the implementation of user story clear? Is the story is small enough?
The conditions for the user story are defined by scrum master in coordination with the product owner. Although the conditions vary for the different projects, some of the common conditions for user story are –
- It is clear and well-written in a format to identify user type, function, and benefits.
- It is self-contained i.e. independent of other user story inherently.
- It is small so that can be delivered in a single sprint.
- It has a defined acceptance criteria for all the functional requirements and appropriate non-functional requirements.
- It should have been estimated by the scrum team.
- All the external blocking dependencies should have been resolved before starting the sprint.
- The resources/team have all the skills required to deliver the sprint.
So, if the user story can give satisfactory answers to the above questions and meet the conditions defined, it is considered to be ready.
Lean software development method follows the principle of “Just in time production”. It aims at increasing the speed of software development and decreasing cost. The basic idea of lean is to reduce non-value-added activities (known as “wastes”) in order to increase customer value. The agile process itself is a lean method for software development lifecycle. However, activities like backlog grooming (when team review items on the backlog to ensure the appropriate items are in the backlog, that they are prioritized well, and that the items at the top of the backlog are ready for delivery) code refactoring (process of restructuring existing computer code – changing the factoring — without changing its external behavior) fits agile methodology more in tune with lean principles.
Yes, the iterative methodology is a process of software development without any interruption. In this method, software development cycles consisting of sprint and release are repeated until the final product is obtained. Whereas, the incremental model is a process of software development where the product is designed, implemented and tested incrementally until the product is finished. It involves both development and maintenance.
The combined effort in the team where one programmer writes the code and the other one reviews it is called pair programming. There are several benefits of pair programming, it not only improves the quality of code but also facilitates the knowledge transfer. It reduces the chance of mistakes as two people are simultaneously working on a code.
The principles of Agile testing are:
- Continuous testing – This ensures the continuous progress of the product. An interesting aspect of the Agile testing process is that unlike the traditional methodologies where only the testing team is focused on product testing, it requires the entire team to participate equally in the testing process.
- Continuous feedback – With every test, the client feedback is encouraged to ensure that the product meets the business requirements of the client.
- Simple and clean code – Whatever errors and defects arise during the testing phase are fixed within the same iteration by the Agile team. This allows for simple, concise, and clean code.
- Less documentation – Agile teams use a reusable checklist. Here, they are more focused on the testing process rather than the incidental details.
Agile manifesto uncovers the better way of developing software by doing it and helping others to do it. Agile has 4 manifesto and 12 principles which defines:
- Individuals and interactions, i.e., self-motivating and self-organized should be encouraged.
- Demonstrate the working software at regular intervals with comprehensive documentation.
- Customers are collaboration over contact negotiation.
- Responding to change over following a plan.
The principles of agile manifesto are-
- Customer Satisfaction: Manifesto provides high priority to satisfy the costumer's requirements. Customer satisfaction is done through early and continuous delivery of valuable software.
- Welcome Change: Making change during software development is common and inevitable. Every changing requirement should be welcome, even in the late development phase. Agile process is used to increase the customer's competitive advantage.
- Deliver the Working Software: Deliver the working software frequently, ranging from a few weeks to a few months with considering the shortest period.
Yes, sometimes we use waterfall module over scrum. This is because when the client requirement is simple, small, well-defined, fully understood, predictable, and the subject does not change until the project complete.
Epic: A customer described software feature that is itemized in the product backlog is known as epic. Epics are sub-divided into stories
User Stories: From the client perspective user stories are prepared which defines project or business functions, and it is delivered in a particular sprint as expected.
Task: Further down user stories are broken down into different task
To improve the performance, the existing code is modified; this is re-factoring. During re-factoring the code functionality remains same
When planning a sprint usually, the velocity of the sprint is measured on the basis of professional judgement based on historical data. However, the mathematical formula used to measure the velocity of the sprint are,
- first – completed story points X team capacity: If you measure capacity as a percentage of a 40 hours weeks.
- Second – completed story points / team capacity: If you measure capacity in man-hours.
For our scenario second method is applicable.
Product backlog: It contains a list of all desired features and is owned by the product owner.
Sprint backlog: It is a subset of the product backlog owned by development team and commits to deliver it in a sprint. It is created in Sprint Planning Meeting
Test driven development or TDD is also known as test-driven design. In this method, developer first writes an automated test case which describes new function or improvement and then creates small codes to pass that test, and later re-factors the new code to meet the acceptable standards.
Prototypes and Wireframes are prototypes that are widely used as part of Empirical Design.
It is used to discuss the difficulty of the story without assigning actual hours. The most common scale used is a Fibonacci sequence ( 1,2,3,5,8,13,….100) although some teams use linear scale (1,2,3,4….), Powers of 2 (1,2,4,8……) and cloth size (XS, S ,M,L, XL).
The tracer bullet is a spike with the current architecture, the current set of best practices, current technology set which results in production quality code. It is not a throw away code but might just be a narrow implementation of the functionality.
A test stub is a small code that replaces an undeveloped or fully developed component within a system being tested. Test stub is designed in such a way that it mimics the actual component by generating specifically known outputs and substitute the actual component.
While working on Agile projects you can use tools like
These are the tips which can be helpful to implement scrum in your project.
- Get your backlog in order
- Get an idea of the size of your product backlog items
- Clarify sprint requirement and duration to complete the sprint backlog
- Calculate the team sprint budget and then break requirements into tasks
- Collaborate workspace- a center of all team discussion, which includes plans, roadmaps, key dates, sketches of functionality, issues, log, status reports, etc.
- Sprint- Make sure you complete one feature at a time before moving on to the next. A sprint should not be abort unless if there is no other option
- Attend a daily stand-up meeting: In meeting you need to mention, what have been achieved since the last meeting, what will they achieve before the next meeting - and is anything holding up their progress
- Use burndown chart to track daily progress. From the burndown chart, you can estimate whether you are on track, or you are running behind
- Complete each features well before moving on to the next
- At the end of the sprint- hold a sprint review meeting, mention what is achieved or delivered in the sprint.
A product roadmap is referred for the holistic view of product features that create the product vision.
Only the Product Owner can cancel the Sprint. It can be canceled before the Sprint timebox limit ends.
- Version One
To ensure that during the final development stage, there is no major problem left behind a code or version or a build is released, which is known as a release candidate. This is equivalent to the final build, and it is used for testing.
- Product Owner: The product owner is an individual who is responsible for increasing the ROI by determining product features, prioritizing these features into a list, what needs to be focused on the upcoming sprint, and much more. These are constantly re-prioritized and refined.
- Scrum Master: This individual helps the team in learning to apply Scrum to ensure optimum business value. The scrum master removes impediments, shields the team from distractions, and enables them to adopt agile practices.
- Scrum Team: They are a collection of individuals who work together to ensure that the requirements of the stakeholders are delivered.
Sprint 0 refers to the small amount of effort put in to create a rough skeleton of the product backlog. It also includes insights towards estimating the release of products. Sprint 0 is required for:
- Creating the project skeleton, along with research spikes
- Keeping minimal design
- Developing some stories completely
- Having low velocity and being lightweight
The spike is a set of activities that involve Extreme Programming (XP) for research, design, investigation, creating POCs, etc. The spike aims to reduce risks of the technical approach, helping gain knowledge to better understand requirements and improve reliability
User story mapping represents and arranges user stories that help with understanding system functionalities, system backlog, planning releases, and providing value to customers. They arrange user stories based on their priority on the horizontal axis. On the vertical axis, they are represented based on the increasing levels of sophistication.
Score creep refers to a change that’s uncontrolled and added without checking its impact on scope, time, cost, etc.
To handle it, here’s what needs to be done:
- Close monitoring of work being done on a day-to-day basis.
- Understanding and communicating the vision to the team and ensuring they’re aligned.
- Capturing, reviewing the project requirements regularly (against what is delivered), to emphasize to the team & customer about the requirements signed off.
- Ensuring that any changes introduced go through change control & are implemented based on the approval for change request.
- Avoid gold plating.
Definition of Done (DoD) refers to the collection of deliverables, which includes written codes, comments on coding, unit tests, integration testing, design documents, release notes, etc. This adds verifiable and demonstrable values to project development. DoD is very helpful to scrum while identifying the deliverables to achieve the objective of the projects It helps with:
- Defining the steps required to deliver the iteration
- The usage of appropriate tools like burndown to make the process more effective
- Ensuring on-time feedback throughout the project life cycle
- Ensuring the walkthrough of the product backlog items are done and understood correctly
- The creation of a checklist for the product backlog items
- Ensuring the DoD is defined to become task-oriented
- Involving the product owner for reviewing during the sprint and sprint retrospective
The term "servant leader" mainly focuses on the service orientation which a leader should demonstrate. The Scrum Master needs to be a facilitator, a guide, a mentor, etc. This helps the team have increased involvement, empowerment, etc.
Want to test this skill? Check out Adaface assessments
Agile Project Management Test
Scrum Master Test
We evaluated several of their competitors and found Adaface to be the most compelling. Great default library of questions that are designed to test for fit rather than memorization of algorithms.