Yeah thats tough. I hate when they do that. The beauty is, it doesnt matter. Usually I just drop a mid number and agile seems to give the flexibility to change that as you identify the true scope of work. Do what you can in the sprint, but eventually update the points to match or break it up and adjust points best you can at that point. Given I haven’t been doing agile long, so I could be missunderstanding how it should work.
I love working on the edge of exploration, but also recognize it’s going to be a lot of dipping the toes in and seeing what the water is like before I can reliably predict these things. I’m fortunate that no one on my team does what I do, so, sometimes they just accept “will report back next week with an estimate based on actual research”.
also not getting ambushed with large hypotheticals beyond our actual tool chain support help but <shrug>
Yeah thats tough. I hate when they do that. The beauty is, it doesnt matter. Usually I just drop a mid number and agile seems to give the flexibility to change that as you identify the true scope of work. Do what you can in the sprint, but eventually update the points to match or break it up and adjust points best you can at that point. Given I haven’t been doing agile long, so I could be missunderstanding how it should work.
I love working on the edge of exploration, but also recognize it’s going to be a lot of dipping the toes in and seeing what the water is like before I can reliably predict these things. I’m fortunate that no one on my team does what I do, so, sometimes they just accept “will report back next week with an estimate based on actual research”.
also not getting ambushed with large hypotheticals beyond our actual tool chain support help but <shrug>