Filter interviews by
I applied via Hirist and was interviewed in Jun 2024. There were 2 interview rounds.
Agile is a methodology that promotes iterative development and collaboration, while Scrum is a specific framework within Agile.
Agile focuses on delivering value to customers through iterative development and continuous feedback.
Scrum is a framework within Agile that defines roles, events, and artifacts to help teams work together effectively.
Scrum includes roles like Scrum Master, Product Owner, and Development Team, a...
Product Owner manages the product backlog.
Product Owner is responsible for prioritizing and maintaining the product backlog.
Scrum Master facilitates the backlog refinement process but does not manage the backlog.
Team members can contribute to the backlog by adding items during sprint planning or refinement sessions.
I applied via Hirist and was interviewed in Apr 2024. There was 1 interview round.
Agile is iterative and flexible, while waterfall is sequential and rigid.
Agile involves continuous feedback and adaptation, while waterfall follows a linear approach.
Agile allows for changes throughout the project, while waterfall requires detailed planning upfront.
Agile focuses on delivering working software in short iterations, while waterfall delivers the final product at the end of the project.
Agile promotes collab...
The product owner handles the product backlog.
The product owner is responsible for prioritizing and maintaining the product backlog.
The product owner works closely with stakeholders to gather requirements and ensure the backlog is up-to-date.
The Scrum team collaborates with the product owner to understand and deliver items from the backlog.
The product owner may delegate some backlog management tasks to the Scrum master
Top trending discussions
I applied via Referral and was interviewed in Aug 2024. There was 1 interview round.
Experienced Scrum Master with a background in software development and a passion for facilitating team collaboration and continuous improvement.
Over 5 years of experience as a Scrum Master in various software development teams
Certified Scrum Master (CSM) with strong knowledge of Agile principles and practices
Facilitated daily stand-up meetings, sprint planning, sprint reviews, and retrospectives
Worked closely with Prod...
I handle a team of 7 members and manage them by facilitating daily stand-ups, sprint planning, retrospectives, and removing impediments.
Facilitate daily stand-ups to keep the team aligned and focused on sprint goals
Lead sprint planning meetings to prioritize tasks and set achievable goals
Conduct retrospectives to reflect on what went well and what can be improved for the next sprint
Remove impediments that are blocking ...
Scrum is time-boxed with fixed iterations, while Kanban is continuous flow with no fixed time-boxes.
Scrum has fixed iterations called sprints, while Kanban has no fixed time-boxes.
Scrum focuses on completing a set amount of work within a sprint, while Kanban focuses on continuous delivery of work.
Scrum limits work in progress by setting a sprint goal, while Kanban limits work in progress based on capacity and flow.
Scru...
Resolved conflicts related to task prioritization, communication issues, and team member disagreements.
Facilitated discussions to prioritize tasks based on business value and team capacity.
Addressed communication breakdowns by encouraging open dialogue and active listening.
Mediated conflicts between team members by helping them understand each other's perspectives.
Implemented team agreements and ground rules to prevent...
Managed risks in sprints by identifying, assessing, and mitigating potential issues to ensure successful delivery.
Identified potential risks at the beginning of the sprint through team discussions and retrospectives
Assessed the impact and likelihood of each risk to prioritize mitigation efforts
Mitigated risks by implementing proactive measures such as adjusting sprint scope or increasing communication
Example: Identifie...
KPIs are Key Performance Indicators used to measure the success of a project. Examples include velocity, sprint burndown, and team happiness.
KPIs are metrics used to evaluate the performance and success of a project
Common KPIs in Agile projects include velocity, sprint burndown, and team happiness
KPIs help teams track progress, identify areas for improvement, and make data-driven decisions
I applied via Approached by Company and was interviewed in May 2024. There were 4 interview rounds.
Team success in Scrum can be measured through various metrics such as velocity, sprint burndown charts, and team satisfaction.
Velocity: Measure the amount of work completed in each sprint. A consistent increase in velocity indicates team success.
Sprint burndown charts: Monitor how well the team is progressing towards completing the sprint goal. A steady burndown chart shows success.
Team satisfaction: Conduct regular re...
I applied via LinkedIn and was interviewed in Sep 2024. There was 1 interview round.
Agile principles are a set of values and beliefs that guide the Agile methodology in software development.
Customer satisfaction through early and continuous delivery of valuable software
Welcome changing requirements, even late in development
Deliver working software frequently, with a preference for shorter timescales
Collaboration between business people and developers throughout the project
Supportive and trusting envir...
Agile ceremonies are regular meetings that help teams collaborate, plan, and review progress in Agile projects.
Examples include Daily Standup, Sprint Planning, Sprint Review, and Retrospective
These ceremonies help teams stay aligned, communicate effectively, and continuously improve
Each ceremony has a specific purpose and timebox to ensure efficiency and productivity
I applied via Naukri.com and was interviewed in May 2024. There was 1 interview round.
I applied via Approached by Company and was interviewed in Jan 2024. There was 1 interview round.
The Agile Manifesto talks about the anti-pattern of excessive documentation.
The Agile Manifesto values 'Working software over comprehensive documentation'.
This principle emphasizes the importance of focusing on delivering working software rather than spending excessive time on documentation.
Excessive documentation can lead to delays, miscommunication, and reduced flexibility in responding to change.
Teams should aim to ...
based on 2 interviews
Interview experience
Software Engineer
5
salaries
| ₹5 L/yr - ₹6 L/yr |
Data Analyst
5
salaries
| ₹3 L/yr - ₹6 L/yr |
Senior Software Engineer
5
salaries
| ₹12 L/yr - ₹26 L/yr |
Senior Technical Lead
4
salaries
| ₹26 L/yr - ₹33 L/yr |
Senior Recruiter
3
salaries
| ₹8.4 L/yr - ₹9 L/yr |
Ninjacart
Crofarm
Aibono
BIGHAAT AGRO