Man, I’m currently in a project which started out with 2 major goals. Pretty early on, we got told that one of the goals is practically impossible, so we decided to ignore that. And we realized the other goal needs to be simplified significantly to be achievable in the slightest, although we still weren’t sure, if it violates the laws of physics.
Now we’re a year into development, we’ve only figured out that it might be physically possible in certain situations. And yesterday, we talked to a guy with domain knowledge, who told us like ten different bigger challenges we’d still have to solve.
So how many story points do you estimate?
Sounds like a medium t-shirt
Apparently, a dev on the customer side estimated that he’d need two weeks to implement the whole project (which thankfully our customer representative also laughed at).
well, the ticket has a due date in 2 weeks so got to be a 7.
That’s not how storypointing works. If the deadline was tomorrow, would it be 1 point?
i know story points as an estimate of complexity or time it takes to get something done. i was also asked many times to estimate stories with a fixed hard deadline thats laughably close to LocalDateTime.now(), aka Stories where someone allready decided that this must be an easy thing to do without knowing jackshit.
what are the story points you are talking about?
There should be one that’s what the sales guy promised to the client. >.>
