Skip to main content

What to do if your SCRUM team finishes early?

This is a good place to be. But if this happens a lot then you may have to look into commitments you are making. You may be committing less.

Work on the next priority items in the backlog. Inform the Product owner. He/she may have some ideas also. You don't have to complete the additional "stories" you pull into the sprint  but if there are stories which you can complete then do it.

Work on those Technical debts which you were pushing out- bug fixes, automation, performance enhancement, CI,CD etc.

If needed , based on the input from Product owner, do some backlog refinement for upcoming sprints.

Maybe its a good idea to learn something new which you might use in upcoming sprints. Do some cross team learning or work on some "new ideas".

If there are multiple teams working on same product go and help other teams. They might do the same for your team in future when you need help and when you are behind in your schedule. 


Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed.

This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team.

Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process.

Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down.

If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also brainstorms idea…

What are the rules of scrum?

A relatively new person to scrum asked me this question last day. My answer to that person was yes. But really does the scrum have any rules? Scrum is a framework which helps us in developing software. It has very few rules and apart from those basic rules rest of them are guidelines like best practices.

Some of the rules 

The roles of Scrum
•Scrum Master -
•Product Owner
•Feature TeamThe PDCA cycle ( )  frequent communication about risks (daily)
•Plan – Sprint planning
•Do – Actual engineering sprint – deliver a potential shippable code
•Check – Sprint review
•Act – Retrospective 
The scrum guide @ will be a good guideline for teams/companies planning to start scrum. If you are following the recommendation in these then you are following scrum.
Apart from these rest of the ceremonies and artifacts are there…

Challenge best practice?

Idea of best practices is a seductive but dangerous trap. … The great danger in “best practices” is that the practice can get disconnected from its intent and its context and may acquire a ritual significance that is unrelated to its original purpose.

They also inhibit a “challenge everything” culture and continuous improvement—a pillar of lean thinking. Why would people challenge ‘best’?