Really enjoy the level of detail you put on each post. Great read! One of my recent struggles was the team to agree on smaller tickets. Unfortunately, historically the team was been using Jira tickets as "documentation". Splitting on smaller tickets would make the "documentation" more difficult to read lol only after implementing a true knowledge storage and sharing system (wiki), I managed to tackle this problem. Having tickets smaller makes it so much easy to predict the effort. For me this is a ninja tactic. Thank you!
Most of the time, it seems that this is the perfect ideal that is never reached. Some teams have better processes, other not. How often do you think this entire process is well-implemented?
Hi Benedikt! Thanks for reading! Very interesting question.
I would say this process for me has been the end state I am constantly looking for my teams to reach. I have never reached the place where all these things are perfect. I don't think anybody ever will.
At the beginning with a team that is starting there is a lot of variability and is difficult to get meaningful metrics but over time the teams have reached to an acceptable state consistently and these methods have helped me estimate in a reasonable way how much the team can do.
And whenever there is a variation, I apply remediation actions. At least with this I am not blind navigating.
Really enjoy the level of detail you put on each post. Great read! One of my recent struggles was the team to agree on smaller tickets. Unfortunately, historically the team was been using Jira tickets as "documentation". Splitting on smaller tickets would make the "documentation" more difficult to read lol only after implementing a true knowledge storage and sharing system (wiki), I managed to tackle this problem. Having tickets smaller makes it so much easy to predict the effort. For me this is a ninja tactic. Thank you!
Thank you so much for reading it Artur! Glad this is helpful!
This is a very thorough write-up!
Most of the time, it seems that this is the perfect ideal that is never reached. Some teams have better processes, other not. How often do you think this entire process is well-implemented?
Hi Benedikt! Thanks for reading! Very interesting question.
I would say this process for me has been the end state I am constantly looking for my teams to reach. I have never reached the place where all these things are perfect. I don't think anybody ever will.
At the beginning with a team that is starting there is a lot of variability and is difficult to get meaningful metrics but over time the teams have reached to an acceptable state consistently and these methods have helped me estimate in a reasonable way how much the team can do.
And whenever there is a variation, I apply remediation actions. At least with this I am not blind navigating.
It probably is a flywheel as well, with teams getting better by themselves. The first steps are hard and then it gets easier with every step.