Showing posts with label Scrum. Show all posts
Showing posts with label Scrum. Show all posts

Sunday, December 2, 2018

Scrum Master Interview Questions

When i am involved in any interview, i focus on a holistic approach.  Each answer is derived based on many factors and these factors differ from team to team and organization to organization.

#1. How do you spent your day at work as a scrum master.

#2. Given that you are in a product backlog grooming session with PO and your project will get over in next 3 iteration. however you only have one iteration of work left. Explain what does this situation mean to a scum master.

#3. A story has 5 tasks and team is done with 90% of tasks. One of the team member raises red flag on this task, as it is non-achievable. After various discussions, PO arrives at a conclusion that this story is not needed. How, you as a scrum master deal with this situation. What actions can this team takes to avoid future issues.

#4. In your Iteration Planning meeting, Team is not able to arrive to a consensus on estimation of a specific story. There are two respectable and senior members are having heated discussion over approach and over all estimates. How you as a scrum master deal with the situation.

#5. Given that you have spent 5 iteration as a team and a team is not able to scale up the velocity and there is no sign of improvement in code quality either. Your retrospectives are not able to identify the underlying problem. How you as scrum master will identify the cause of the issues and help team identify a corrective action. Explain role of scrum master in whole process.

#6. How will you ensure and motivate a team to increase various non functional requirements like unit test code coverage or efficient UI in product delivery. 

#7. What are the top 3 metrics you use in your project to report health of the project.

#8.  My organization is moving to agile and identifies Jane, a Technical Manager as a scrum master. Based on the organization structure she is also responsible for rating team members and Jane is responsible for delivering a robust architecture. Few team members report to Jane. Jane is an ace developer and passionate about technology.

Explain, how Jane can effectively perform her roles and responsibility as scrum master. 


#9. Why stories are estimated in Fibonacci, what is so special in this series. Can we use some other series of set of numbers?

#10. Explain different kind of estimation techniques used in agile?

#11. What are top three things which you should validate before a story is moved to an iteration?

#12. What are the components of DOR in your project?

#13. What are the components of DOD in your project?

#14. How to perform a release plan in agile for long project when you do not have historical background of team velocity?


#15. How do you coach/mentor a PO when they are coming from NON agile mind set. How do you coach them to align them self with agile?

#16. How do you perform Agile retrospective with your teams?

#17. What will you do when middle of the iteration you identify that a story is either over estimated or underestimated?

#18. What are Scrum Values

#19, What are scrum ceremonies and output of each one of them

#20. Define Agile?




Sunday, March 26, 2017

Burndown Chart, narrates you a story

Burndown chart

Burndown chart provides remaining effort for a given period of time. This is one of the simplest metrics team normally adopt to measure the progress of sprint or release.

It also represent the velocity at which you are completing your customer stories.

During a typical development life cycle, following two flavors of burn down chart can be used:
1. Sprint Burndown and
2. Release Burndown

Scope of the article is to describe Sprint Burn down and narrate a story to your stakeholders

Expected Burndown chart
Assumptions
a. Lets assume that team will complete a project with all user/customer stories in  Nine iterations.
b. Scrum team burns 10 pts of story size in an iteration. This is a velocity of scrum team

It shows amount of work remaining and work done during each iteration.
Ideal Burn down chart
Ideal Burn down chart
Legends:
Y-Axis: Work Remaining
X- Axis: Effort (in story points)

Such a simple brundown chart can tell you following story about the progress:
1. Current iteration = 6th
2. Remaining iterations = 3
3. You and your team have completed 40 story points of effort
4. Looking at the burn down chart you can narrate following story:

"Team has maintained a velocity of 10 story points and will complete the user/customer stories right on time. No major defects re introduced in the product and team is able to take care of them efficiently"  

In reality - How a burn down chart look

Team never sees an ideal burn down chart. The velocity of the team changes every iteration and there is no straight line trend.
Each sprint demonstration or QA process results in a change to the development. This change could because of many reasons, for now let me consider the below two probable cause:

a. Defects identified and reported
b. Feedback from end of sprint demo

Thus effecting : a. Scope, b. Time, c. Cost and Quality of deliverable.


Below image shows a typical Burndown of a project?










Above chart is a result of one or more causes listed below (not limited to below list):

1. Scope discovery
2. Team member leaves the project
3. Natural disaster
4. Scope creep (function creep, feature creep, requirement creep,..)
5. Requirement change
6.  Reported bugs/defect in the system

I have a story for my stakeholders by just looking at above burn down chart.


- See more at about Burndown chart @ scrumalliance.org