Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Should the incidences of continuous improvement, Spikes and delivery be estimated, based on agility?


I hace the next question:

Should the incidences of continuous improvement, Spikes and delivery be estimated? 

These incidents require effort, but I would like to know what is the best practice.

I appreciate your help!!!

Lina A.


2 answers

1 accepted

2 votes
Answer accepted
Earl McCutcheon
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
May 31, 2022

Hi @Lina Marcela Almanza P_ ,

Thanks for reaching out to the community, and this is a good question but also really hard to answer as this blog post sums it up really well in the first line:

Estimation is hard. For software developers, it's among the most difficult — if not the most difficult — aspects of the job.

Best practices in estimation are to start off loose and tighten up the numbers as you figure out what works best, and how the team operates over a few sprints.  And realistically experimentation while watching the outcomes is going to be the best approach to find out what works best for defining your team's workload. 

Currently, If you are including the inflated estimates to compensate for spikes, or delays and are constantly coming in way under the deadline, the best approach is to reign in the estimates to a tighter estimate value so you can add in additional workload knowing that the team will make the deadline under those tighter estimates.  However in juxt position, if you are not including those options for some additional leeway but are constantly running into scope creep and delays in releases due to unforeseen blockers or underestimating, then the opposite is true and you will want to start giving the estimates a bit more breathing room.

Along with the blog post mentioned above, I also recommend checking out "How to choose the best methods of estimation for planning" as well.


1 vote
John Funk
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Feb 05, 2023

Hi @Lina Marcela Almanza P_ 

I am marking Earl's response as Answer Accepted. Please let us know if you still have questions. 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events